Hypercard is a terrific product when it comes to integrating graphics, sound and text. This has resulted in some very creative images. Unfortunately, the result has simultaneously led to stacks with a lot of white space and redundancy. In creating the first few stacks, while I learn Hypercard's capabilities, I have tried to balance 'user-friendliness' with practicality. Functions which should be infrequent (adding a new card), don't have a button - the edit menu does a pretty good job.
At the same time, I have tried to use Hypercard's unique abilities - as in the handling of the State & Zip fields. A 'lesson' from relational databases is present in the handling of the miscellaneous information.
The other point to remember is that the stack is still evolving. As I discover new capabilities, I am incorporating them into the stack. Consequently, the current handling of the 'go to spouse' button leaves something to be desired.